fix: ensure datetime in post request is normalized #543
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Currently, in
POSTrequests to/search, with datetime values are not normalized as they are inGETrequests to/search, which can cause different results to be returned for the same datetime filter. For example:POSTrequest to/searchwithdatetime=2025-11-20T09:54:38Z/2025-11-20T09:54:38Zreturns an item with2025-11-20T09:54:38.196614Z, whereas a GET request with the same datetime filter does not which is expected behavior. This PR ensures that datetime values inPOSTrequests are normalized in the same way as inGETrequests.PR Checklist:
pre-commit run --all-files)make test)